Reviewing files that changed from the base of the PR and between e6a2d3c and cbfb6ab.

• databases/cockroachdb/bun.lock is excluded by !**/*.lock
• databases/postgresql-supabase/bun.lock is excluded by !**/*.lock
• databases/prisma-postgres/bun.lock is excluded by !**/*.lock

• databases/cockroachdb/package.json (1 hunks)
• databases/cockroachdb/prisma/schema.prisma (2 hunks)
• databases/cockroachdb/src/script.ts (1 hunks)
• databases/cockroachdb/tests/prisma.test.ts (1 hunks)
• databases/postgresql-supabase/package.json (1 hunks)
• databases/postgresql-supabase/prisma.config.ts (1 hunks)
• databases/postgresql-supabase/prisma/schema.prisma (1 hunks)
• databases/postgresql-supabase/prisma/seed.ts (1 hunks)
• databases/postgresql-supabase/script.ts (1 hunks)
• databases/prisma-postgres/package.json (1 hunks)
• databases/prisma-postgres/prisma.config.ts (1 hunks)
• databases/prisma-postgres/prisma/schema.prisma (2 hunks)
• databases/prisma-postgres/src/caching.ts (1 hunks)
• databases/prisma-postgres/src/queries.ts (1 hunks)

databases/prisma-postgres/prisma.config.ts (1)

1-12: LGTM! Configuration follows Prisma v6 patterns.

The configuration correctly uses defineConfig with dotenv integration and environment-based datasource URL, aligning with the new Prisma configuration approach.

databases/cockroachdb/package.json (1)

9-26: LGTM! Dependencies aligned with adapter-based client.

The package updates correctly introduce tsx, @prisma/adapter-pg, and align Prisma package versions to support the new generated client approach with adapters.

databases/prisma-postgres/package.json (1)

5-16: LGTM! Package updates support the new Prisma Accelerate configuration.

The migration to tsx and removal of @prisma/extension-accelerate align with the new pattern of configuring Accelerate via PrismaClient options instead of extensions.

databases/prisma-postgres/prisma/schema.prisma (1)

2-4: LGTM! Generator configuration follows Prisma v6+ patterns.

The migration to provider = "prisma-client" with explicit output path and engineType = "client" is the correct approach for the new ESM-ready client that will become the default in Prisma v7.

Based on learnings

databases/prisma-postgres/src/queries.ts (1)

1-6: LGTM! Updated to use generated client with Accelerate configuration.

The changes correctly migrate to the generated Prisma client and configure Accelerate via the accelerateUrl option, replacing the extension-based approach.

databases/postgresql-supabase/package.json (1)

6-19: LGTM! Package updates support adapter-based client configuration.

The migration to tsx and addition of @prisma/adapter-pg correctly enable the new adapter-based approach for PostgreSQL/Supabase connections.

databases/postgresql-supabase/prisma/seed.ts (1)

1-9: LGTM! Adapter initialization follows the correct pattern.

The changes properly migrate to the generated Prisma client with PrismaPg adapter configuration, using the connection string from environment variables.

databases/prisma-postgres/src/caching.ts (1)

1-5: Add import 'dotenv/config' at line 2 of caching.ts.

The code uses process.env.DATABASE_URL but is missing the dotenv import. Since the script runs directly via tsx ./src/caching.ts (as defined in package.json), it needs to explicitly load environment variables. The queries.ts file has this import on line 2—caching.ts should match that pattern.

⛔ Skipped due to learnings

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-webpack-turborepo/packages/database/package.json:13-13
Timestamp: 2025-08-22T12:12:24.602Z
Learning: When analyzing changes from package.json seed scripts to "prisma db seed", always verify the actual content of prisma.config.ts rather than relying solely on regex patterns, as the configuration may be properly defined but in a format that doesn't match overly restrictive search patterns.

Learnt from: aidankmcalister
Repo: prisma/prisma-examples PR: 8334
File: orm/fastify-graphql-sdl-first/src/context.ts:1-1
Timestamp: 2025-10-27T13:18:46.546Z
Learning: In the prisma/prisma-examples repository, generated Prisma client files (typically at paths like `prisma/generated/client`) are intentionally not committed to the repository. These files are generated at build/test time. Do not flag missing generated client artifacts as issues in reviews.

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/graphql-auth/prisma/schema.prisma:2-4
Timestamp: 2025-10-15T13:58:59.096Z
Learning: The "prisma-client" generator provider (introduced in Prisma v6) is the newer, ESM-ready alternative to "prisma-client-js". It requires an explicit output path and is better suited for modern runtimes, edge deployments, and will become the default in Prisma v7. Use "prisma-client" for new projects or when modernizing existing projects.

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/fastify-graphql/prisma/schema.prisma:2-4
Timestamp: 2025-10-15T13:58:29.130Z
Learning: In Prisma v6.15 and later, `provider = "prisma-client"` is a valid generator configuration value when combined with `engineType = "client"`. This configuration generates a Prisma client without Rust engine binaries, relying on JavaScript driver adapters instead, and is different from the traditional `provider = "prisma-client-js"` configuration.

Learnt from: AmanVarshney01
Repo: prisma/prisma-examples PR: 8327
File: orm/graphql-subscriptions/prisma/schema.prisma:1-5
Timestamp: 2025-10-15T13:56:01.807Z
Learning: In Prisma v6.15 and later, `engineType = "client"` is a valid generator configuration value that generates a Prisma client without Rust engine binaries, relying on JavaScript driver adapters instead (e.g., prisma/adapter-pg). This is useful for edge and serverless deployments.

Learnt from: FGoessler
Repo: prisma/prisma-examples PR: 8260
File: generator-prisma-client/nextjs-starter-turbopack/components/quotes.tsx:1-1
Timestamp: 2025-08-22T12:12:43.161Z
Learning: In Next.js applications using Prisma, the connection() function from 'next/server' serves a different purpose than 'export const dynamic = force-dynamic'. The connection() function ensures proper database connection context and request isolation, while dynamic = 'force-dynamic' only controls rendering strategy. Both should be used together and are not redundant.

databases/cockroachdb/src/script.ts (1)

1-11: LGTM! Clean migration to adapter-based client.

The changes correctly implement the Prisma v6 adapter-based pattern: importing from the generated client path, setting up the PrismaPg adapter with the connection string, and initializing PrismaClient with the adapter. This aligns with the schema's new generator configuration.

Based on learnings

databases/cockroachdb/prisma/schema.prisma (1)

1-5: LGTM! Proper migration to the new Prisma client generator.

The generator configuration correctly adopts the "prisma-client" provider with engineType = "client" and explicit output path. This modern approach generates an ESM-ready client without Rust binaries, relying on JavaScript driver adapters (PrismaPg), and is well-suited for edge deployments.

Based on learnings

databases/postgresql-supabase/prisma.config.ts (1)

1-12: LGTM! Well-structured Prisma configuration.

The configuration file correctly uses defineConfig for type-safe setup, loads environment variables with dotenv/config, and properly specifies the schema, migrations, and datasource paths. This aligns with the modern Prisma configuration approach.

databases/postgresql-supabase/script.ts (1)

1-9: LGTM! Consistent adapter-based migration.

The changes properly implement the adapter-based pattern: importing from the generated client, setting up the PrismaPg adapter, and initializing PrismaClient with the adapter. The pattern is consistent with the CockroachDB example and aligns with the new generator configuration in the schema.

Based on learnings

databases/postgresql-supabase/prisma/schema.prisma (1)

4-8: LGTM! Proper generator configuration for adapter-based client.

The generator configuration correctly migrates to "prisma-client" provider with engineType = "client" and explicit output path. This setup generates an ESM-ready client that relies on JavaScript driver adapters (PrismaPg), matching the pattern used in the CockroachDB example and aligning with Prisma v6+ best practices.

Based on learnings